System, method, and computer-readable medium for configuration of an IP-femtocell system

ABSTRACT

A system, method, and computer readable medium for configuration of a femtocell system is provided. A femtocell system is provisioned with a default base station manager IP address. The base station manager receives an account identifier of a user subscription and a femtocell system ID assigned to the femtocell system. The base station manager may allocate a SID/NID for the femtocell system. A list of electronic serial numbers of handsets in the user subscription may be compiled by the base station manager. The femtocell system may connect with the base station manager and request a configuration download once deployed in a SOHO. The compiled electronic serial numbers may then be transferred from the base station manager to the femtocell system in a configuration download.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional patent applicationSer. No. 61/003,151 entitled SIP-IOS ADAPTER FUNCTION filed Nov. 15,2007, the disclosure of each of which is incorporated in its entiretyherein by reference.

FIELD OF THE INVENTION

The present invention is generally related to radio access technologiesand, more particularly, to mechanisms for configuration of a femtocellsystem.

BACKGROUND OF THE INVENTION

Contemporary cellular radio systems, or mobile telecommunicationsystems, provide an over-the-air interface to wireless user equipments(UEs) via a radio access network (RAN) that interfaces with at least onecore network. The RAN may be implemented as, for example, a CDMA2000RAN, a Universal Mobile Telecommunications System (UMTS) RAN, a GlobalSystem for Mobile communications (GSM) RAN, or another suitable radioaccess network implementation. A UE may comprise, for example, a mobileterminal such as a mobile telephone, a laptop computer featuring mobiletelephony software and hardware, a personal digital assistant (PDA), orother suitable equipment adapted to transfer and receive voice or datacommunications with the radio access network.

A RAN covers a geographical area comprised of any number of cells eachcomprising a relatively small geographic area of radio coverage. Eachcell is provisioned by a cell site that includes a radio tower, e.g., abase transceiver station (BTS), and associated equipment. BTSscommunicate with UEs over an air interface within radio range of theBTSs.

Numerous BTSs in the RAN may be communicatively coupled to a basestation controller, also commonly referred to as a radio networkcontroller (RNC). The BSC manages and monitors various system activitiesof the BTSs serviced thereby. BSCs are coupled with at least one corenetwork.

BTSs are typically deployed by a carrier network in areas having a highpopulation density. The traffic capacity of a cell site is limited bythe site's capacity and affects the spacing of cell sites. In suburbanareas, sites are often up to two miles apart, while cell sites deployedin dense urban areas may be as close as one-quarter of a mile apart.Because the traffic capacity of a cell site is finitely limited, as isthe available frequency spectrum, mobile operators have a vestedinterest in technologies that allow for increased subscriber capacity.

A microcell site comprises a cell in a mobile phone network that coversa limited geographic area, such as a shopping center, hotel, airport, orother infrastructure that may have a high density mobile phone usage. Amicrocell typically uses power control to limit the radius of themicrocell coverage. Typically a microcell is less than a mile wide.

Although microcells are effective for adding network capacity in areaswith high mobile telephone usage, microcells extensively rely on theRAN, e.g., a controlling BSC and other carrier functions. Becausecontemporary BSCs have limited processing and interface capacity, thenumber of BTSs—whether microcell BTSs or typical carrier BTSs—able to besupported by the BSC or other RAN functions is disadvantageouslylimited.

Contemporary interest exists in providing enterprise and office access,including small office/home office (SOHO) radio access, by an evensmaller scale BTS. The radio coverage area of such a system is typicallyreferred to as a femtocell. In a system featuring a femtocell, a UE maybe authorized to operate in the femtocell when proximate the femtocellsystem, e.g., while the UE is located in the SOHO. When the UE movesbeyond the coverage area of the femtocell, the UE may then be servicedby the carrier network. The advantages of deployment of femtocells arenumerous. For instance, mobile users frequently spend large amounts oftime located at, for example, home, and many such users rely extensivelyon cellular network service for telecommunication services during thesetimes. For example, a recent survey indicated that nearly thirteenpercent of U.S. cell phone customers do not have a landline telephoneand rely solely on cell phones for receiving telephone service. From acarrier perspective, it would be advantageous to have telephone servicesprovisioned over a femtocell system, e.g., deployed in the user's home,to thereby reduce the load, and effectively increase the capacity, onthe carrier RAN infrastructure. However, various issues related torestricting femtocell access to authorized user equipment devices remainunresolved.

Therefore, what is needed is a mechanism that overcomes the describedproblems and limitations.

SUMMARY OF THE INVENTION

The present invention provides a system, method, and computer readablemedium for configuring a femtocell system for deployment in a network.In one implementation, a femtocell system is provisioned with a defaultbase station manager IP address. The base station manager receives anaccount identifier of a user subscription and a femtocell system IDassigned to the femtocell system. The base station manager may allocatea SID/NID for the femtocell system. A list of ESNs of handsets in theuser subscription may be compiled by the base station manager. Thefemtocell system may connect with the base station manager and request aconfiguration download once deployed in a SOHO. The compiled electronicserial numbers may then be transferred from the base station manager tothe femtocell system in a configuration download. The femtocell systemmay then screen electronic serial numbers of user equipments thatattempt to register with the femtocell system. In another embodiment,the femtocell system may be factory-configured with a base stationmanager redirector uniform resource locator (URL). On startup, thefemtocell system may connect with the redirector and obtain a gateway IPaddress therefrom, e.g., based on a femtocell system ID, a registeredlocation of the femtocell system, or other back office criteria.Thereafter, the femtocell system may connect with the gateway andestablish carrier network and core network connections for provisioningof services to user equipment.

In one embodiment of the disclosure, a method for configuring afemtocell system for deployment in a network is provided. The methodincludes provisioning the femtocell system with a network address of adefault base station manager, receiving at least one identifier of auser equipment in a customer plan of a customer associated with thefemtocell system, obtaining at least one electronic serial number of theuser equipment, and configuring the femtocell system to screen any userequipment that attempts to register with the femtocell system with theat least one electronic serial number.

In another embodiment of the disclosure, a computer-readable mediumhaving computer-executable instructions for execution by a processingsystem, the computer-executable instructions for configuring a femtocellsystem for deployment in a network, is provided. The computer-readablemedium includes instructions for provisioning the femtocell system witha network address of a default base station manager, receiving at leastone identifier of a user equipment in a customer plan of a customerassociated with the femtocell system, obtaining at least one electronicserial number of the user equipment, issuing, by the femtocell system, arequest for a configuration download, and configuring the femtocellsystem to screen any user equipment that attempts to register with thefemtocell system with the at least one electronic serial number.

In a further embodiment of the disclosure, a system for configuring afemtocell system for deployment in a network is provided. The systemincludes a packet-switched network including a base station managerserver that receives an identifier of a user equipment in a customerplan of a customer associated with the femtocell system and obtains anelectronic serial number of the user equipment, an Internet Protocolmultimedia subsystem communicatively interfaced with the packet-switchednetwork, and a femtocell system communicatively coupled with thepacket-switched network adapted to provide a radio interface with a userequipment and that is provisioned with an Internet Protocol address ofthe base station manager server, wherein the femtocell system issues, tothe base station manager server, a request for a configuration downloadand receives the configuration download including the electronic serialnumber in response to issuance of the request, and wherein the femtocellsystem screens any user equipment that attempts to register with thefemtocell system with the at least one electronic serial number.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network system thatincludes a cellular network adapted to provide macro-cellular coverage;

FIG. 2 is a diagrammatic representation of a conventional network systemconfiguration featuring a femtocell;

FIG. 3 is a diagrammatic representation of a network system in which afemtocell system implemented in accordance with an embodiment of thepresent invention may be deployed;

FIG. 4A is a simplified diagrammatic representation of the femtocellsystem depicted in FIG. 3 that may be connected with an IP backhaul inaccordance with an embodiment;

FIG. 4B is a simplified diagrammatic representation of an alternativeembodiment of a femtocell system that may be connected with an IPbackhaul;

FIG. 5 is a diagrammatic representation of an exemplary sessioninitiation protocol registration message generated by a femtocell systemon behalf of a user equipment in accordance with an embodiment;

FIG. 6 is a diagrammatic representation of a network system featuring afemtocell network implemented in accordance with an embodiment;

FIG. 7 is a diagrammatic representation of an exemplary softwareconfiguration of a user equipment adapted for engaging in communicationswith femtocell systems in accordance with an embodiment;

FIG. 8 depicts a flowchart of a femtocell system configurationprovisioning routine implemented in accordance with an embodiment;

FIG. 9 is a configuration routine that facilitates generation offemtocell system configuration data implemented in accordance with anembodiment; and

FIG. 10 is a flowchart of a femtocell startup routine that facilitatesnetwork setup of a femtocell system in accordance with an embodiment.

DETAILED DESCRIPTION OF THE INVENTION

It is to be understood that the following disclosure provides manydifferent embodiments or examples for implementing different features ofvarious embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting.

FIG. 1 is a diagrammatic representation of a network system 100 thatincludes a cellular network 110 adapted to provide macro-cellularcoverage to a user equipment. Cellular network 110 may comprise, forexample, a code-division multiple access (CDMA) network, such as aCDMA-2000 network.

Cellular network 110 may include any number of base transceiver stations(BTSs) 112 a-112 c communicatively coupled with a base stationcontroller (BSC) 114 or RNC. Each individual BTS 112 a-112 c under thecontrol of a given BSC may define a radio cell operating on a set ofradio channels thereby providing service to a user equipment (UE) 125,such as a mobile terminal. BSC 114 manages the allocation of radiochannels, receives measurements from mobile terminals, controlshandovers, as well as various other functions as is understood. BSC 114is interconnected with a mobile services switching center (MSC) 116 thatprovides mobile terminal exchange services. BSC 114 may be additionallycoupled with a packet data serving node (PDSN) 118 or other gatewayservice that provides a connection point between the CDMA radio accessnetwork and a packet network, such as Internet 160, and providesmobility management functions and packet routing services. MSC 116 maycommunicatively interface with a circuit switched network, such as thepublic switched telephone network (PSTN) 150, and may additionally becommunicatively coupled with an interworking function (IWF) 122 thatprovides an interface between cellular network 110 and PSTN 150.

System 100 may also include a signaling system, such as a signalingsystem #7 (SS7) network 170. SS7 network 170 provides a set of telephonysignaling protocols which are used to set up the vast majority of theworld's PSTN telephone calls. SS7 network 170 is also used in cellularnetworks for circuit switched voice and packet-switched dataapplications. As is understood, SS7 network 170 includes varioussignaling nodes, such as any number of service control points (SCPs)172, signal transfer points (STPs) 174, and service switching points(SSPs) 176.

BTSs 112 a-112 c deployed in cellular network 110 may service numerousnetwork 110 subscribers. Cell cites provided by BTSs 112 a-112 ccommonly feature site ranges of a quarter to a half mile, e.g., indensely populated urban areas, to one to two miles in suburban areas. Inother remotely populated regions with suitable geography, site rangesmay span tens of miles and may be effectively limited in size by thelimited transmission distance of relatively low-powered UEs. As referredto herein, a cell provided by a BTS deployed in carrier network 110 foraccess by any authorized network 110 subscriber is referred to as amacrocell.

FIG. 2 is a diagrammatic representation of a conventional network system200 configuration featuring a femtocell. In the depicted example, acentral BSC 214 deployed in a cellular carrier network 210 may connectwith a soft switch core 212 that is connected with a MSC 216. MSC 216connects with the cellular core network and may interface with othernetworks, such as the PSTN as is understood. BSC 214 may be connectedwith and service numerous BTSs 212 a-212 c that provide macrocells tocellular network 210 subscribers.

BSC 214 may additionally connect with a tunnel gateway system 218 thatis adapted to establish secured tunnels 232 a-232 x with respectivefemtocell systems 250 a-250 x. Femtocells comprise cellular accesspoints that connect to a mobile operator's network using, for example, aresidential DSL or cable broadband connection. Femtocells 250 a-250 xprovide a radio access point for UE 225 when the UE is within range of afemtocell system with which the UE has authorized access. For example,femtocell system 250 a may be deployed in a residence of the user of UE225. Accordingly, when the user is within the residence, mobiletelecommunications may be provided to UE 225 via an air-interfaceprovided by femtocell system 250 a. In this instance, UE 225 iseffectively offloaded from the macro BTS, e.g., BTS 212 a, andcommunications to and from the UE are carried out with femtocell system250 a over Internet 260. Thus, femtocell systems 250 a-250 x may reducethe radio resource demands by offloading UEs from macrocells tofemtocells and thereby provide for increased subscriber capacity ofcellular network 210.

In contemporary implementations such as that depicted in FIG. 2, afemtocell system 250 a comprises a transceiver without intelligence andis thus required to be connected and managed by BSC 214. Thus, femtocellsystems 250 a-250 x are reliant on the carrier network centralized BSC214 which has limited capacity and thus does not exhibit desirablescaling characteristics or capabilities. Moreover, high communicationsoverhead are realized by the BTS backhaul.

FIG. 3 is a diagrammatic representation of a network system 300 in whicha femtocell system implemented in accordance with an embodiment of theinvention may be deployed. System 300 includes a radio access network(RAN) 310 that provides an over-the-air interface with a UE 325, e.g., amobile terminal. RAN 310 may comprise, for example, a CDMA radio accessnetwork or another suitable RAN. RAN 310 may comprise various BTSs andassociated base station controllers (BSCs) as well as otherinfrastructure as is understood. UE 325 may be implemented as a personaldigital assistant (PDA), a mobile phone, a computer, or another deviceadapted to interface with RAN 310.

System 300 may include an IP Multimedia Subsystem (IMS) 320 architectureadapted to provide IP service to UE 325. To this end, RAN 310 iscommunicatively coupled with a serving general packet radio service(GPRS) support node (SGSN) 314 and a gateway GPRS support node (GGSN)316. SGSN 314 provides the delivery of data packets from and to UE 325within its service area. GGSN 316 provides an interface between the GPRSbackbone network and external packet data networks. GGSN 316 iscommunicatively coupled with a policy decision function (PDF) 318 thatprovides authorization of media plane resources, e.g., quality ofservice (QoS) authorizations, policy control, bandwidth management, andthe like. PDF 318 may be communicatively coupled with a call sessioncontrol function (CSCF) 320.

CSCF 320 comprises various session initiation protocol (SIP) servers orproxies that process SIP signaling packets in IMS 320. CSCF 320 mayinclude a proxy-CSCF (P-CSCF) that provides a first point of contact foran IMS-compliant UE. The P-CSCF may be located in the visited network,or in the UE's home network if the visited network is not fullyIMS-compliant. UE 325 may discover the P-CSCF, e.g., by using DynamicHost Configuration Protocol (DHCP), or by assignment in a packet dataprotocol (PDP) context. CSCF 320 additionally includes a Serving-CSCF(S-CSCF) that comprises the central node of the signaling plane. TheS-CSCF comprises a SIP server, but additionally performs sessioncontrol. The S-CSCF is located in the home network and interfaces with ahome subscriber server (HSS) 340 to download and upload user profiles.CSCF 320 further includes an Interrogating-CSCF (I-CSCF) that comprisesa SIP function located at the edge of an administrative domain. TheI-CSCF has an IP address that is published in the Domain Name System(DNS) 372 that facilitates location of the I-CSCF by remote servers.Thus, the I-CSCF is used as a forwarding point for receipt of SIPpackets within the domain.

HSS 340 comprises a user database that supports the IMS network entitiesthat manage calls. HSS 340 stores user profiles that specifysubscription-related information of authorized users, authenticates andauthorizes users, and provides information about the user's physicallocation. Various application servers (AS) 342 a-342 n that host andexecute services interface with CSCF 320 via SIP.

CSCF 320 is coupled with a breakout gateway control function (BGCF) 322that comprises a SIP server that provides routing functionality based ontelephone numbers. BGCF 322 is used when a UE places a call from the IMSto a phone in a circuit switched network, e.g., PSTN 330, or the publicland mobile network. A media gateway controller Function (MGCF) 324performs call control protocol conversion between SIP and ISDN User Part(ISUP) and interfaces with a signaling gateway (SGW) 326. SGW 326interfaces with the signaling plane of a circuit switched network, e.g.,PSTN 330. SGW 326 may transform lower layer protocols, such as StreamControl Transmission Protocol (SCTP), into the Message Transfer Part(MTP) protocol, and pass ISUP data from MGCF 324 to PSTN 330 or anothercircuit switched network. A media gateway (MGW) 328 interfaces with themedia plane of PSTN 330 or another circuit switched network byconverting data between real-time transport protocol (RTP) and pulsecode modulation (PCM), and may also be employed for transcoding when thecodecs of the IMS and circuit switched networks differ. Resources of MGW328 are controlled by MGCF 324. Fixed access, e.g., IP telephony devices374 a-374 b, may connect with IMS network via Internet 370 that iscommunicatively coupled with IMS network 320 by way of border gateway360.

As is understood, DNS 372 comprises a scalable namespace thatfacilitates access to entities deployed on the Internet or privatenetworks. DNS 372 maintains various records for host names, servers, andthe like. For example, DNS 372 maintains records (commonly referred toas “A records”) that map hostnames to IP addresses, pointer (PTR)records that map IP addresses to canonical names to facilitate reverseDNS lookups, service (SRV) records that specify information on availableservices, naming authority pointer (NAPTR) records that facilitateregular expression based rewriting, and various other records. DNS 372may additionally include a telephone number mapping (ENUM) system thatfacilitates resolution of SIP addresses from E.164 number as isunderstood.

A base station manager (BSM) 378 may be deployed in Internet 370 and maybe adapted to communicate with numerous femtocell systems and femtocellnetworks. BSM 378 may provide various operations, maintenance, andmanagement functions to femtocell systems. For example, BSM 378 mayprovide service provisioning of femtocell systems, e.g., by providingconfiguration downloads to femtocell systems and preloading defaultconfiguration data for femtocell systems distributed via sales channels.BSM 378 may provide various support and maintenance features, such asalarm and periodic statistics reporting, automatic remote software imagedistribution to femtocell systems, provide upgrades andreconfigurations, and may provide remote access via Internet 370 fordiagnostics and customer support. In accordance with an embodiment, afemtocell system may be factory-configured with a URL of the BSM 378 oranother network node configured as a redirector. On startup, thefemtocell system connects with the BSM or redirector and obtains agateway IP address therefrom. Thereafter, the femtocell system mayconnect with the gateway and establish connections with a carrier andcore network.

In accordance with an embodiment, a femtocell system 350 may includeintegrated BTS and BSC functions and may feature additional capabilitiesavailable in the provided femtocell site coverage area. Femtocell system350 provides an IP-accessible radio access network, is adapted foroperation with IMS 320, and provides radio link control functions.Femtocell system 350 may be communicatively coupled with Internet 370via any variety of backhaul technologies, such as an 802.11x link, a10/100 BaseT LAN link, a T1/E1 Span or fiber, cable set top box, DSLmodem connected with a central office digital subscriber line accessmultiplexer, a very small aperture terminal (VSAT), or another suitablebackhaul infrastructure.

In an embodiment, femtocell system 350 includes a session initiationprotocol (SIP) adapter that supports a SIP client pool and providesconversion of call set-up functions to SIP client set-up functions. Forexample, a SIP client pool allocated by femtocell system 350 maycomprise a plurality of SIP user agents 352 a-352 c that each may beallocated for a UE authorized to access femtocell system 350.Additionally, femtocell system 350 includes electronic serial number(ESN) screening, and/or Mobile Equipment Identifier (MEID) screening, toallow only designated UEs to access the femtocell thereby restrictingaccess to authorized home or small office UEs. For example, femtocellsystem 350 may be configured with an ESN and/or MEID list 354 thatspecifies ESNs and/or MEIDs of UEs authorized to access femtocell system350. In the illustrative example, ESNs of “ESN 1”-“ESN 3” are includedin ESN list 354. Provisioning of ESN(s) and/or MEID(s) may be made aspart of an initial femtocell system 350 activation. In the illustrativeexample, femtocell system 350 is allocated an Internet Protocol (IP)address of “66.249.73.42”, and UE 325 is allocated a mobile servicesISDN (MSISDN) number, or E.164 number, of “12145551212”.

FIG. 4A is a simplified diagrammatic representation of femtocell system350 depicted in FIG. 3 that facilitates provisioning of a femto-RAN inaccordance with an embodiment. Femtocell system 350 includes an antenna400 coupled with a BTS 410. BTS 410 may be implemented, for example, asa 1×RTT ASIC device and may comprise a non-diversity receiver featuringa built-in duplexer. In an embodiment, BTS 410 may feature only oneoperational band and may include a transmitter scan receiver and localoscillator. BTS 410 may be communicatively coupled with a BSC 420 thatprovides radio control functions, such as receiving measurements fromUEs, such as mobile phones, control of handovers to and from otherfemtocell systems, and may additionally facilitate handoff to or frommacrocells.

Femtocell system 350 includes an electronic serial number screeningfunction 430 that may facilitate approving or rejecting service for a UEby femtocell system 350. Additionally femtocell system 350 includes anInternet Operating System (IOS) and SIP Adapter (collectively referredto as IOS-SIP Adapter 440). IOS-SIP adapter 440 may invoke and manageSIP clients, such as a user agent (UA) pool comprising one or more UAs.In accordance with an embodiment, each UE 325 authorized to be servicedby femtocell system 350 may have a UA allocated therefor by thefemtocell system in a manner that facilitates transmission ofcommunications to and from a UE over an IP backhaul. Accordingly, whenan authorized UE is within the femtocell system 350 site range,telecommunication services may be provided to the UE via the IP backhauland the femtocell system 350 provisioned RAN. When the UE is movedbeyond the service range of femtocell system 350, telecommunicationservices may then be provided to the UE via macrocellular coverage.

To facilitate routing of calls from circuit switched call originators,femtocell system 350 may perform a DNS/ENUM registration on behalf ofUEs authorized to obtain service from femtocell system 350. In thepresent example, assume UE 325 with a MSISDN of “12145551212” has a SIPservice subscription in the domain “example.com” and has a SIP uniformresource identifier (URI) of “12145551212@example.com”. An exampleDNS/ENUM registration message generated by femtocell system 350 onbehalf of UE 325 and transmitted to DNS 372 is as follows:

$ORIGIN 2.1.2.1.5.5.5.4.1.2.1.e164.arpa. IN NAPTR 100 10 “u” “E2U+sip”“!{circumflex over ( )}.*$!sip:12145551212@example.com!”.

As is understood, the first line of the registration message comprisesthe MSISDN number of the UE converted (i.e., reversed with each numeraldelineated with a “.” character and appended with the e164.arpa domain)for DNS lookup. The second line of the registration message specifiesthe NAPTR record for the hosts that can further process the address—thedomain “example.com” (in which the UE with a URI of12145551212@example.com is registered) in the present example.

Femtocell system 350 may generate and issue a SIP registration on behalfof UE 325 authorized for service access by femtocell system 350.

FIG. 4B is a simplified diagrammatic representation of an alternativefemtocell system 450 that facilitates provisioning of a femto-RAN inaccordance with an alternative embodiment. Femtocell system 450 includesan antenna 400 coupled with a radio node (RN) 411. RN 411 may beimplemented, for example, as a 1×EV-DO ASIC device. For example, RN 411may provide a 1×EV-DO Rev. 0 air interface or a 1×EV-DO Rev. A airinterface. RN 411 may be communicatively coupled with a radio networkcontroller (RNC) 421 that provides radio control functions, such asreceiving measurements from UEs, control of handovers to and from otherfemtocell systems, and may additionally facilitate handoff to or frommacrocells. RNC 421 may also provide encryption/decryption functions,power, load, and admission control, packet scheduling, and various otherservices.

Femtocell system 450 includes an electronic serial number screeningfunction 430 that may facilitate approving or rejecting service for a UEby femtocell system 450. Additionally, femtocell system 450 includes anInternet Operating System (IOS) and SIP Adapter (collectively referredto as IOS-SIP Adapter 440). IOS-SIP adapter 440 may invoke and manageSIP clients, such as a user agent (UA) pool comprising one or more UAs.Each UE 325 authorized to be serviced by femtocell system 450 may have aUA allocated therefor by femtocell system 450 in a manner thatfacilitates transmission of communications to and from a UE over an IPbackhaul. Accordingly, when an authorized UE is within the femtocellsystem 450 site range, telecommunication services may be provided to theUE via the IP backhaul and femtocell system 450 provisioned RAN. Whenthe UE is moved beyond the service range of femtocell system 450,telecommunication service may then be provided to the UE viamacrocellular coverage. Femtocell system 450 may perform a DNS/ENUMregistration on behalf of UEs authorized to obtain service fromfemtocell system 450 and may generate and issue a SIP registration onbehalf of a UE authorized for service access by the femtocell system 450in a manner similar to that described above with reference to femtocellsystem 350.

FIG. 5 is a diagrammatic representation of an exemplary SIP registrationmessage 500 generated by femtocell system 350 on behalf of UE 325authorized for service access thereby in accordance with an embodiment.Registration message 500 may be transmitted from femtocell system 350 toa location service, such as a SIP registrar implemented as SIP Registrar380. Registrar 380 may provide the location and contact information tolocation service 382. Registration message 500 includes a REGISTER field510 that specifies the registration is being made within the domain“example.com”. In accordance with an embodiment, multiple contacts areincluded in registration message 500. In the present example,registration message 500 includes a contact field 512 that specifies aSIP contact for UE 325. Notably, the SIP contact field 512 for UE 325specifies the UA registered on behalf of UE with the URI12145551212@example.com is located at the IP address of “66.249.73.42”.That is, the SIP contact registered by femtocell system 350 on behalf ofUE 325 is to be addressed at the femtocell system 350 address of66.249.73.42 thereby resulting in routing of SIP signaling messages tofemtocell system 325. In turn, femtocell system 350 may convert SIP callset up messaging to RAN signaling, allocate an uplink and a downlinkchannel for UE 325, and set up a call or data session thereon.

In the present example, registration message 500 includes a secondcontact field 514 that specifies a telephone URI, e.g., the MSISDN+1-214-555-1212 of UE 325. Thus, a location query for the SIP URIsip:12145551212@example.com would return two contacts. The first is theSIP URI that can be used to reach femtocell system 350, and thus UE 325thereby, and the second is the telephone URI that can be used to reachUE 325 via macrocellular coverage, i.e., via RAN 310. As is understood,the order of contacts 512-514 provides a contact preference, and themultiple contacts may be registered in separate registration messages.The depicted registration message including both the SIP contact URI andtelephone URI is exemplary only. Accordingly, in the present example, anattempt to contact UE 325 may first be made via the SIP URI12145551212@example.com. In the event that the session is notsuccessfully set up via the SIP contact, an attempt may be made to setupa session via RAN 310 using the telephone URI.

When the UE 325 moves outside the coverage area of femtocell system 350,another registration may be generated and submitted by femtocell system350 on behalf of UE 325 where the telephone URI is designated as thepreferred contact. Further, the SIP URI may be removed from theregistration when the UE 325 moves outside the coverage area offemtocell system 350 thereby avoiding any attempts to establish asession with UE 325 via femtocell system 350 when UE 325 has movedbeyond the femtocell system 350 coverage area.

In accordance with an embodiment, a network of femtocell systems may bedeployed and connected with an IP backhaul. In this implementation, anauthorized UE may be serviced by the femtocell network, and service maybe transferred from one femtocell to another femtocell via a femtocellhandoff procedure. In the event that the femtocell network is deployedin an area serviced by a macrocellular network, handoff routines mayprovide preference for transferring a UE to a target femtocell systemrather than a macrocell site. In the event that a suitable femtocell isunavailable for handoff of a UE, the UE may be transferred to themacrocell site. In configurations featuring a large number of femtocellsystems, a network in which the femtocell systems are deployed mayinclude multiple gateways. In such an implementation, the femtocellsystem may be factory-configured with a base station manager redirectoruniform resource locator (URL) or a URL of another network entityconfigured as a redirector. On startup, the femtocell system connectswith the BSM or redirector and obtains a gateway IP address therefrom.The femtocell system may then connect with the gateway and establishconnections with, for example, a carrier network and core network asdescribed more fully hereinbelow.

FIG. 6 is a diagrammatic representation of a network system 600featuring a femtocell network implemented in accordance with anembodiment of the invention. System 600 includes a RAN 610 that providesan over-the-air interface with a UE 625, e.g., a mobile terminal. RAN610 may comprise, for example, a CDMA radio access network or anothersuitable RAN. RAN 610 may comprise various BTSs 612 a-612 c andassociated BSCs 604 as well as other infrastructure as is understood.Each of BTSs 612 a-612 c provides a respective macrocell 602 a-602 cthat may provide telecommunication service to UE 625. BSC 604 is coupledwith a MSC 606 that provides cellular exchange services, mobilitymanagement, and other services within the area that it serves as isunderstood.

RAN 610 may interface with IMS 620 adapted to provide IP service to UE625. To this end, RAN 610 may be communicatively coupled with a SGSN 614and a GGSN 616. GGSN 616 is communicatively coupled with a PDF 618 thatprovides authorization of media plane resources. PDF 618 may becommunicatively coupled with a CSCF 620.

CSCF 620 comprises various SIP servers or proxies that process SIPsignaling packets in IMS 620. CSCF 620 may include a P-CSCF, a S-CSCF,and an I-CSCF as is understood. HSS 640 stores user profiles thatspecify subscription-related information of authorized users,authenticates and authorizes users, and provides information about theuser's physical location. Various application servers 642 a-642 n mayhost and execute services and is interfaced with CSCF 620 via SIP.

The I-CSCF has an IP address that is published in DNS 672 thatfacilitates location of the I-CSCF by remote servers. Thus, the I-CSCFis used as a forwarding point for receipt of SIP packets within thedomain.

CSCF 620 is coupled with a BGCF 622 that comprises a SIP server thatprovides routing functionality based on telephone numbers. A MGCF 624performs call control protocol conversion between SIP and ISDN User Part(ISUP) and interfaces with a SGW 626 that itself interfaces with thesignaling plane of a circuit switched network, e.g., PSTN 630. A MGW 628interfaces with the media plane of PSTN 630 or another circuit switchednetwork. Resources of MGW 628 are controlled by MGCF 624. Fixed accessdevices, e.g., IP telephony devices 674 a-674 b, may connect with IMSnetwork via Internet 670 that is communicatively coupled with IMSnetwork 620 by way of border gateway 660.

A BSM 678 may be deployed in Internet 670 and may be adapted tocommunicate with numerous femtocell systems and femtocell networks. BSM678 may provide various operations, maintenance, and managementfunctions to femtocell systems. BSM 678 may provide service provisioningof femtocell systems, e.g., by providing configuration downloads tofemtocell systems and preloading default configuration data forfemtocell systems distributed via sales channels. BSM 678 may providevarious support and maintenance features, such as alarm and periodicstatistics reporting, automatic remote software image distribution tofemtocell systems, provide upgrades and reconfigurations, and mayprovide remote access via Internet 670 for diagnostics and customersupport.

Femtocell systems 650 a-650 c may include integrated BTS and BSC, oralternatively (or additionally) radio node (RN) and radio networkcontroller (RNC), functions and may feature additional capabilitiesavailable in the provided femtocell site coverage areas. Femtocellsystems 650 a-650 c provide an IP-accessible radio access network, areadapted for operation with IMS 620, and provide radio link controlfunctions. Femtocell systems 650 a-650 c may be communicatively coupledwith Internet 670 via any variety of backhaul technologies, such as an802.11x link, a 10/100 BaseT LAN link, a T1/E1 Span or fiber, cable settop box, DSL modem connected with a central office digital subscriberline access multiplexer, a very small aperture terminal (VSAT), oranother suitable backhaul infrastructure. In the illustrative example,femtocell systems 650 a-650 c may be coupled with an IP backhaul accessdevice 655, such as an Ethernet cable or DSL router, that may becommunicatively coupled with a gateway, e.g., a gateway 676 a. Forinstance, a femtocell system may be coupled with access node 655 viarespective 10/100 BaseT twisted pair cables, Category 5 cabling, orother suitable interconnection. In systems featuring a large number offemtocell systems, or femtocell systems that are deployed over asubstantial geographic region, multiple gateways 676 a-676 b may bedeployed for access to, for example, Internet 670, a carrier networksuch as radio access network 610, or a core network. In such animplementation, a femtocell system may be provisioned with a URL of BSM678 that is configured as a redirector. Alternatively, the femtocellsystem may be provisioned with a URL of another network entityconfigured as a redirector. On startup, the femtocell system may connectwith the BSM or redirector according to the factory-provisioned URLthat, in turn, provides an IP address of a gateway, e.g., gateway 676 aor 676 b, with which the femtocell system is to connect as describedmore fully hereinbelow with reference to FIG. 10.

Each of femtocell systems 650 a-650 c provide a respective femtocellsite 651 a-651 c in which UE 625 may be provided telecommunicationservices over an air interface. Femtocell systems 650 a-650 c arecommunicatively coupled with one another via access device 655.Femtocells 650 a-650 c deployed for conjunctively providing a femtocellservice coverage area comprised of the collective femtocell sites 651a-651 c are collectively referred to herein as a femtocell network. Inan embodiment, femtocell systems 650 a-650 c may exchange messages withone another to facilitate handoff of a UE from one femtocell to another,e.g., as UE 625 moves out of the radio range of a femtocell and into theradio range of another. In the depicted example, the femtocell networkprovided by femtocell systems 650 a-650 c is at least partiallyoverlapped by one or more macrocell sites 602 a-602 c provisioned bymacrocell BTSs 612 a-612 c. In such an implementation, femtocell systems650 a-650 c may provide preference to another femtocell for handoff of aUE thereto. In the event that another femtocell is not available or isunsuitable for a handoff, the UE may then be transferred tomacrocellular coverage via a handoff to a macrocell BTS.

In an embodiment, each of femtocell system 650 a-650 c include arespective SIP adapter that supports a SIP client pool and providesconversion of call set-up functions to SIP client set-up functions.Additionally, femtocell systems 650 a-650 c include ESN screening toallow only designated UEs to access the femtocells thereby restrictingaccess to authorized home or small office UEs. For example, femtocellsystem 650 a may be configured with an ESN and/or MEID list 654 a thatspecifies ESNs of UEs authorized to access femtocell system 650. In theillustrative example, ESNs of “ESN 1”-“ESN 3” are included in ESN list654 a. Provisioning of ESN(s) may be made as part of an initialfemtocell system 650 activation. Other femtocell systems 650 b-650 c maybe similarly configured with an ESN list including ESNs of UEsauthorized to access the femtocell system network comprised of femtocellsystems 650 a-650 c. In the illustrative example, femtocell systems 650a-650 c are allocated a respective IP address of “66.249.73.42”,“66.249.73.43”, and “66.249.73.44”, and UE 625 is allocated a MSISDNnumber, or E.164 number, of “12145551212”.

FIG. 7 is a diagrammatic representation of an exemplary softwareconfiguration 700 of a UE, such as UE 625, adapted for engaging incommunications with femtocell systems in accordance with an embodiment.In the exemplary configuration of FIG. 7, the UE is configured withaccess network-specific software entities 760, e.g., protocol and driversoftware associated with a particular access network technology, such asCDMA, GSM, UMTS, or another suitable radio access network, and isdependent on the particular cellular and femtocell access technology inwhich the UE is to be deployed. While configuration 700 depicts a UEadapted for deployment in a single access network technology type, theUE may be implemented as a multi-mode device and may accordingly includea plurality of access-specific entities in accordance with anembodiment. The particular configuration 700 is illustrative only and isprovided only to facilitate an understanding of embodiments disclosedherein.

In the illustrative example, configuration 700 includes a cellular modemdriver 702 for providing a physical interface with the access network inwhich the UE is deployed. An access-stratum 704 and a non-access stratum706 may be included in configuration 700. A cellular radio interface 708may be communicatively coupled with lower layers of configuration 700and may additionally interface with network and session managementlayers, e.g., a network stack 710. Configuration 700 may include anoperating system 714, such as Symbian, Blackberry O/S, or anotheroperating system suitable for mobile applications, and may coordinateand provide control of various components within the UE.

Configuration 700 may include a femto application 712 that facilitatesfemtocell network acquisition and handoff of a UE from a macrocellularnetwork to a femtocell system in accordance with an embodiment.

Configuration 700 may include a preferred roaming list (PRL) 716 thatcontains information used during the system selection and acquisitionprocess. PRL 716 indicates which bands, sub-bands and service provideridentifiers will be scanned, and the priority of the scan order. In theillustrative example, PRL 716 includes four entries 716 a-716 d thatrespectively specify four networks (illustratively designated “Femto”,“Macro 1”, “Macro 2”, and “Roam 1”). In the present example, assume“Femto” refers to the network of femtocell systems 650 a-650 c. Thefemtocell network is specified first in the prioritized list of PRLentries and thus indicates that the femtocell network is the preferredaccess network. Assume “Macro 1” refers to radio access network 610, and“Macro 2” refers to another cellular network. “Roam 1” specified by PRLentry 716 d may refer to another cellular network that may have aroaming agreement with the UE home network. As is understood, PRL 716may comprise an acquisition table that specifies a list of frequenciesassociated with each of the networks specified in the roaming list onwhich the UE may scan during search of a particular system and mayfurther specify PN offsets thereof. The acquisition table mayadditionally specify a network type of each listed network andassociated channel blocks.

In accordance with an embodiment, femtocell systems 650 a-650 c includeESN screening to allow only designated UEs to access the femtocellsthereby restricting access to authorized home or small office UEs. Tothis end, mechanisms for configuration of femtocell systems 650 a-650 cwith authorized UE ESNs are provided in accordance with embodiments.

FIG. 8 depicts a flowchart 800 of a femtocell system configurationprovisioning routine implemented in accordance with an embodiment. Theprovisioning routine is invoked (step 802), and the femtocell system maybe provisioned with an ID (step 804). The femtocell system may then beprovisioned with a default BSM IP address (step 806), e.g., the IPaddress of BSM 678. Provisioning of the femtocell system ID and defaultBSM IP address may, for example, be made at the factory or productionfacility of the femtocell system or, alternatively, at a point of saleentity. The femtocell system may then be deployed in a small office/homeoffice network (step 808). In an alternative embodiment, the femtocellsystem may additionally or alternatively be provisioned with a URL ofthe BSM configured as a redirector or to another redirector networkentity. The femtocell system may then request and receive aconfiguration download (step 810), e.g., from the default BSM. Inaccordance with an embodiment, the configuration download may include anESN list that specifies ESN(s) and/or MEID(s) of UE(s) authorized toaccess the femtocell system. The provisioning routine cycle may then end(step 812).

FIG. 9 depicts a flowchart 900 of a configuration routine thatfacilitates generation of femtocell system configuration dataimplemented in accordance with an embodiment.

The configuration routine is invoked (step 902), and an accountidentifier and femtocell ID may be received (step 904), e.g., at adefault BSM. Handset IDs in the customer plan associated with thefemtocell system may then be received (step 906). A femtocell systemidentification number (SID)/network identification number (NID) may thenbe allocated for the femtocell system (step 908). ESNs of UEs authorizedto access then femtocell system may then be compiled (step 910), e.g.,from customer account information. The configuration information maythen be transferred to the femtocell system (step 912), e.g., uponrequest of the configuration information from the femtocell system. Theconfiguration information may include ESN(s) of UEs authorized to accessthe femtocell system. Optionally, the configuration information mayinclude the PRL of one or more UEs authorized to access the femtocellsystem. In this instance, the femtocell system may transfer the PRL tothe UE over an air-interface. On receipt of the configurationinformation, the femtocell system may load the ESN list including theESNs of UEs authorized to access the femtocell system.

FIG. 10 is a flowchart 1000 of a femtocell startup routine thatfacilitates network setup of a femtocell system in accordance with anembodiment.

It is assumed that the femtocell system has been factory-provisionedwith pre-loaded data including, for example, a femtocell identity/mediaaccess control (MAC) address and a first contact identification. In aparticular implementation, the first contact identification comprises aredirector URL, e.g., a URL of the BSM 678 in the event that the BSM isconfigured as a redirector. To this end, the BSM 678 may be configuredwith an equipment register 679 that stores femtocell system identifyinginformation, e.g., femtocell IDs assigned to femtocell systems, operatorspecific data, etc. Alternatively, the URL may reference another networkentity configured as a redirector.

The startup routine is invoked (step 1002), e.g., on femtocell systempower-up, and local Internet connections are established with thefemtocell system (step 1004). For example, local dynamic hostconfiguration protocol (DHCP)/DNS transactions may be made as well aslocal network address translation and firewall transactions. Thefemtocell system may then connect with a BSM 678 configured as aredirector or other suitably configured redirector network entity (step1006). In one implementation, the femtocell system may connect with theredirector according to a URL that is factory-provisioned or otherwisepre-loaded in the femtocell system and that is assigned to theredirector-configured BSM or other network entity. When connecting withthe redirector, the femtocell system may transmit a femtocell system IDassigned to the femtocell system (step 1008). The redirector may theninterrogate the equipment register 679 and return an IP address of agateway to the femtocell system, e.g., one of gateways 676 a-676 b, withwhich the femtocell system is to connect (step 1010). For example, theparticular gateway selected by the redirector may be determined based ona registered location of the femtocell system that is correlated withthe femtocell system ID or other back office criteria. In this manner,femtocell systems may be deployed in a multi-gateway network. Thefemtocell system may then connect with the gateway (step 1012) which maybe implemented as a security gateway. In this instance, the femtocellsystem may establish a secure connection with the gateway (step 1014),e.g., an IPSec tunnel, and connections may then be established with thecarrier network (step 1016), e.g., access network 610. BSM downloadtransactions may then be made between the femtocell system and the BSM678 (step 1018), e.g., software version checks and downloads,configuration downloads, and location verification transactions. IMS andcore network connections may then be established (step 1020), and thestartup routine cycle may then end (step 1022) after which alarm andstatistics transactions, BSM client operation transactions, and calland/or data services may be performed by the femtocell system.

As described, a communication system featuring an IP-based femtocellsystem for provisioning communication services to a user equipment isprovided. In one implementation, a femtocell system is provisioned witha default base station manager IP address. The base station managerreceives an account identifier of a user subscription and a femtocellsystem ID assigned to the femtocell system. The base station manager mayallocate a SID/NID for the femtocell system. A list of ESNs of handsetsin the user subscription may be compiled by the base station manager.The femtocell system may connect with the base station manager andrequest a configuration download once deployed in a SOHO. The compiledESNs may then be transferred from the base station manager to thefemtocell system in a configuration download. The femtocell system maythen screen ESNs of user equipments that attempt to register with thefemtocell system.

The flowcharts of FIGS. 8-9 depict process serialization to facilitatean understanding of disclosed embodiments and are not necessarilyindicative of the serialization of the operations being performed. Invarious embodiments, the processing steps described in FIGS. 8-9 may beperformed in varying order, and one or more depicted steps may beperformed in parallel with other steps. Additionally, execution of someprocessing steps of FIGS. 8-9 may be excluded without departing fromembodiments disclosed herein.

The illustrative block diagrams depict process steps or blocks that mayrepresent modules, segments, or portions of code that include one ormore executable instructions for implementing specific logical functionsor steps in the process. Although the particular examples illustratespecific process steps or procedures, many alternative implementationsare possible and may be made by simple design choice. Some process stepsmay be executed in different order from the specific description hereinbased on, for example, considerations of function, purpose, conformanceto standard, legacy structure, user interface design, and the like.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singleprocessor or multiple processors. Additionally, various steps ofembodiments of the invention may provide one or more data structuresgenerated, produced, received, or otherwise implemented on acomputer-readable medium, such as a memory.

Although embodiments of the present invention have been illustrated inthe accompanied drawings and described in the foregoing description, itwill be understood that the invention is not limited to the embodimentsdisclosed, but is capable of numerous rearrangements, modifications, andsubstitutions without departing from the spirit of the invention as setforth and defined by the following claims. For example, the capabilitiesof the invention can be performed fully and/or partially by one or moreof the blocks, modules, processors or memories. Also, these capabilitiesmay be performed in the current manner or in a distributed manner andon, or via, any device able to provide and/or receive information.Further, although depicted in a particular manner, various modules orblocks may be repositioned without departing from the scope of thecurrent invention. Still further, although depicted in a particularmanner, a greater or lesser number of modules and connections can beutilized with the present invention in order to accomplish the presentinvention, to provide additional known features to the presentinvention, and/or to make the present invention more efficient. Also,the information sent between various modules can be sent between themodules via at least one of a data network, the Internet, an InternetProtocol network, a wireless source, and a wired source and viaplurality of protocols.

What is claimed is:
 1. A method of configuring a femtocell system fordeployment in a network, comprising: provisioning the femtocell systemwith a network address of a default base station manager; receiving atleast one identifier of a user equipment in a customer plan of acustomer associated with the femtocell system; obtaining at least oneelectronic serial number of the user equipment; comparing the at leastone electronic serial number of the user equipment to a list of knownelectronic serial numbers received and stored by the femtocell systemduring the provisioning; configuring the femtocell system to screen anyuser equipment that attempts to register with the femtocell system withthe at least one electronic serial number, by only allowing the userequipment with the known electronic serial numbers to access thefemtocell network; generating a registration message on behalf of theuser equipment assuming the user equipment is allowed to access thefemtocell system, the registration message permitting call routing andcomprising a user equipment specific identifier and a record identifierindicating at least one host that can process a domain identifier usedto identify the user equipment, the registration message furthercomprising a uniform resource identifier (URI) identifying the networkassociated with the femtocell system and another URI associated with acellular telephone network associated with the user equipment; andtransmitting the registration message from the femtocell system to alocation service to identify the user equipment.
 2. The method of claim1, wherein provisioning the femtocell system with the network addresscomprises provisioning the femtocell system with an Internet Protocoladdress of the default base station manager.
 3. The method of claim 1,wherein obtaining at least one electronic serial number furthercomprises obtaining, by the default base station manager, the at leastone electric serial number.
 4. The method of claim 1, further comprisingconnecting the femtocell system with the default base station mangerover a network.
 5. The method of claim 4, further comprising issuing, bythe femtocell system, a request for a configuration download.
 6. Themethod of claim 5, further comprising transmitting, by the default basestation manger, the configuration download to the femtocell system,where the configuration download includes the at least one electronicserial number.
 7. The method of claim 1, further comprising allocating,by the default base station manager, a system identificationnumber/network identification number for the femtocell system.
 8. Themethod of claim 7, further comprising transmitting, by the default basestation manger, a configuration download to the femtocell system thatincludes the system identification number/network identification number.9. A non-transitory computer-readable storage medium havingcomputer-executable instructions for execution by a processing system,the computer-executable instructions for configuring a femtocell systemfor deployment in a network, the non-transitory computer-readablestorage medium comprising instructions for: provisioning the femtocellsystem with a network address of a default base station manager;receiving at least one identifier of a user equipment in a customer planof a customer associated with the femtocell system; obtaining at leastone electronic serial number of the user equipment; comparing the atleast one electronic serial number of the user equipment to a list ofknown electronic serial numbers received and stored by the femtocellsystem during the provisioning; issuing, by the femtocell system, arequest for a configuration download; configuring the femtocell systemto screen any user equipment that attempts to register with thefemtocell system with the at least one electronic serial number, by onlyallowing the user equipment with the known electronic serial numbers toaccess the femtocell network; generating a registration message onbehalf of the user equipment assuming the user equipment is allowed toaccess the femtocell system, the registration message permitting callrouting and comprising a user equipment specific identifier and a recordidentifier indicating at least one host that can process a domainidentifier used to identify the user equipment, the registration messagefurther comprising a uniform resource identifier (URI) identifying thenetwork associated with the femtocell system and another URI associatedwith a cellular telephone network associated with the user equipment;and transmitting the registration message from the femtocell system to alocation service to identify the user equipment.
 10. The non-transitorycomputer-readable storage medium of claim 9, wherein the instructionsfor provisioning the femtocell system with the network address compriseinstructions for provisioning the femtocell system with an InternetProtocol address of the default base station manager.
 11. Thenon-transitory computer-readable storage medium of claim 9, wherein theinstructions for obtaining at least one electronic serial number furthercomprise instructions for obtaining, by the default base stationmanager, the at least one electric serial number.
 12. The non-transitorycomputer-readable storage medium of claim 9, further comprisinginstructions for connecting the femtocell system with the default basestation manger over a network.
 13. The non-transitory computer-readablestorage medium of claim 12, further comprising instructions fortransmitting, by the default base station manger, the configurationdownload to the femtocell system, where the configuration downloadincludes the at least one electronic serial number.
 14. Thenon-transitory computer-readable storage medium of claim 9, furthercomprising instructions for allocating, by the default base stationmanager, a system identification number/network identification numberfor the femtocell system.
 15. The non-transitory computer-readablestorage medium of claim 14, further comprising instructions fortransmitting, by the default base station manger, a configurationdownload to the femtocell system, where the configuration downloadincludes the system identification number/network identification number.16. A system for configuring a femtocell system for deployment in anetwork, comprising: a packet-switched network including a base stationmanager server that receives an identifier of a user equipment in acustomer plan of a customer associated with the femtocell system andobtains an electronic serial number of the user equipment; an InternetProtocol multimedia subsystem communicatively interfaced with thepacket-switched network; and a femtocell system communicatively coupledwith the packet-switched network adapted to provide a radio interfacewith a user equipment and that is provisioned with an Internet Protocoladdress of the base station manager server, where the femtocell systemissues, to the base station manager server, a request for aconfiguration download and receives the configuration download includingthe electronic serial number in response to issuance of the request,wherein the femtocell system is configured to compare the at least oneelectronic serial number of the user equipment to a list of knownelectronic serial numbers received and stored by the femtocell systemduring the provisioning of the femtocell system, and wherein thefemtocell system screens any user equipment that attempts to registerwith the femtocell system with the at least one electronic serial numberby only allowing the user equipment with the known electronic serialnumbers to access the femtocell network wherein the femtocell systemgenerates a registration message on behalf of the user equipmentassuming the user equipment is allowed to access the femtocell system,the registration message permitting call routing and comprising a userequipment specific identifier and a record identifier indicating atleast one host that can process a domain identifier used to identify theuser equipment, the registration message further comprising a uniformresource identifier (URI) identifying the network associated with thefemtocell system and another URI associated with a cellular telephonenetwork associated with the user equipment; and wherein the femtocellsystem transmits the registration message to a location service toidentify the user equipment.
 17. The system of claim 16, where the basestation manger server allocates a system identification number/networkidentification number for the femtocell system.
 18. The system of claim17, where the configuration download includes the system identificationnumber/network identification number.
 19. The system of claim 16,further comprising a macrocellular system with which the user equipmenthas authorized access.
 20. The system of claim 16, wherein theconfiguration download includes a plurality of electronic serial numberseach associated with a respective user equipment of a customer accountassociated with the user equipment.